>>78028011It doesn't have have support for defragging? No source code for that either? It will need TRIM support, too.
>>78028699Wondering they're going to use a ton of the XP source or rework it into ReactOS.
Can anyone make a list of what needs to be done? This anon
>>78027829 had a good idea.
1. Working AMD64 toolchain and completel 64bit version of the OS.
2. Porting of the included IA64 EFI bootloader.
3. Security fixes.
4. Modernization of codebase.
5. Multiprocessor/multithreading support (should be part of the OS honestly, it's 2020).
6. Btrfs/ZFS (I recommend Ext4 support, too).
7. Porting x86 assembly to Power ISA/SPARC/RISC-V (also suggesting other various processors).
8. Suggestion: Opening a Git repo out of MS's jurisdiction.
9. Suggestion: Removal of all MS watermarks/tattoos/hashes (if possible).
10. Suggestion: Including basic coreutils (cat, ls, grep, top, dir, mkdir, rm, etc).
11. Suggestion: ELF/bin support.
12. Suggestion: Somehow allow newer GPUs and hardware drivers to work just fine (trick them into thinking is Windows 10? No idea.)
14. Defrag and TRIM support for modern HDDs and SSDs.
15.
Also, what compiler is everyone using to get this to work? GCC/G++?
My knowledge of programming is very, very, very basic C, basic Python scripting, some bash scripts and intermediate HTML/CSS. Not sure how much help I can be.
I don't see a Git repo anywhere or any sort of collaborative software management repository. Maybe I missed it. I know it's illegal as shit but we'll see if someone can circumvent that. It'd make things a lot easier.
